Love the draft/prototype! Would love to see this make it into the project down the line I think it looks amazing!

Built onto my real phone. Thanks so much for making this available. 👍

Awesome work !

Feat request

• Is it possible to change the y-axis of the graph in order to be more center on the data like in the app?
  
  

• Maybe the blue area can replace the settings of the upper / lower limit, because it can change in the day. Or maybe the blue area should be displayed with no limit like the other graphs

• In order to have the graph with full width, the status ring could be in the bottom bar

Bugs found

• Sometime on iPhone 13 Pro the live activity don't appear. I have to Disable and Enable it in the settings to have it again.

I have been using this for several days - I really enjoy having it attached to Loop.

Bug report:

• Dynamic Island expanded (long press on dynamic island)
  • truncates the display when glucose is in mg/dL and above 99 mg/dL
  • graphic below with 24 hour display disabled (top) and enabled (bottom)

Feature requests:

• see the target range shown on the Look Screen Widget graph
• see if an override is currently enabled, definitely added to target display on graph, possibly with the override name displayed

Thanks for all the feedback:

• The truncate bug has been fixed @marionbarker
• Also I added the blue area (glucose targets) & the preset to the views, so thank you for the ideas @marionbarker @bastienmoulia .
• @bastienmoulia I have enabled some extra logging for myown device to research the issue regarding the disappearing of the Live Activity.

Preview

Blue area (glucose target)	Preset enabled (without predictive line)	Preset enabled (with predictive line)

Nice upgrade except the override appears confused.

• This override was active from 11:05 to 1:05 pm (with 2 hours duration), but it shows as being currently active (1:45 pm).
• I see the same pattern when long-pressing the dynamic island.
• I updated with the latest commit at 1:21 pm local (after this override had expired).

• I added a new override at 1:47 pm that has a duration of 3 hours.
• I will report back in 20 minutes or so. Long enough to see if the start point is correct
• And then I will turn it off and see what the plots look like.

The walking override started at 1:47 with a duration of 3 hours and was cancelled 19 minutes later.

• upper plot: While override is active. The bad news is the start point for the plot for both lock screen and dynamic island expanded plot is "now" instead of when override started.
• lower plot: After disabling the override. The good news is that plotting a cancelled override was not repeated - perhaps that was related to the new build, or perhaps because it was cancelled instead of allowed to run the full duration.

Thanks for the blue area!

Same here for the bug with an override label shown even none were triggered

I did a bit more testing.

• If an override is active, it is shown as starting "now"
• If an override expires after the planned duration, it continues to be show starting "now"
• If an override is cancelled early, no extraneous override is displayed

In the last update, I didn't see the target area for the next hour by default:

If I activate the premeal, then remove it, it's ok.

Status

Live Activity controls work as expected.
LGTM.

Test

Test again with the latest updates. Focus on the whether the configuration displays the just-modified selections after a change. (Before they were enacted, but the screen did not update right away.)

Configuration

IPhone SE 3rd gen, running iOS 18.3.2

• LoopWorkspace dev, commit 3d48a5c
• update Loop branch from this PR plus commit from PR 2298 (fix error accidentally introduced with PR 2295)

Test Save Button and Configuration Display

The Save button acts appropriately again (see this comment for details). This behavior is related to iOS 18 - older tests for this PR were with iOS 17.

Initially, the Live Activity screen Save button was inactive

• Modify the Live Activity Mode from Large to Small, Save button becomes active
• Tap save and save button becomes inactive
• Tap back and return, Mode of Small is correctly displayed
• Modify the Live Activity Mode from Small to Large, Save button becomes active
• Tap back (without saving) and then return
  • Success: Mode still shows as Small and the Save button is inactive

Comprehensive Tests for Save Button and Configuration Display

Tests below include looking at the Live Activity on the Lock Screen. For "success", the LA must match the displayed configuration.

Repeat test for all rows on the Live Activity screen:

• success: Enabled
• success: Mode
• success: Add predictive line (Large mode only)
• success: Use BG coloring
• success: Upper limit
• success: Lower limit

Test Bottom Row configuration screen

Tests below include looking at the Live Activity on the Lock Screen. For "success", the LA must match the displayed configuration.

• success: delete one item, save button active - back and return, no change
• success: delete one item, save button active- save, back and return, change is displayed on screen
• success: add one item, save button active - back and return, no change
• success: add one item, save button active- save, back and return, change is displayed on screen
• success: rearrange order, save button active - back and return, no change
• success: rearrange order, save button active- save, back and return, change is displayed on screen

@marionbarker Change request is pushed!

Resolution Needed

This code does not build as is because of 2 problems.

Once I resolved both of these in my local copy of your feat/live-activity branch, the code built and live-activity is displayed on my test phone (SE 3rd generation).

1. I made a mistake and merged a fix meant for tidepool-merge branch into dev for the Bolus Progress display glitch. I later fixed it with another PR that merged to dev at a later time - you picked up the first half of the fix (PR 2295) and not the second when you merged dev into your branch. Please update with latest Loop dev that includes PR 2298.

2. Turns out a couple of hard coded values for IPHONEOS_DEPLOYMENT_TARGET are in the Loop.xcodeproj/project.pbxproj file (blame says about 2 years ago).

This is from dev branch, and those lines are also there in feat/live-activity branch (at lines 5085 and 5195).

Loop % grep -n IPHONEOS_DEPLOYMENT_TARGET Loop.xcodeproj/project.pbxproj
4996:				IPHONEOS_DEPLOYMENT_TARGET = 15.1;
5106:				IPHONEOS_DEPLOYMENT_TARGET = 15.1;

The lines with hard-coded values in Loop.xcodeproj/project.pbxproj need to be removed for the value of IPHONEOS_DEPLOYMENT_TARGET in Loop.xcconfig to be recognized. But since that change came in with a tidepool sync in 2023 Loop PR 1991 - let's find out if @ps2 wants a separate PR to remove those, or have that removal come in with this feature branch.

It's ok to remove IPHONEOS_DEPLOYMENT_TARGET settings in this PR.

@marionbarker fixed! branch is up-to-date with dev and removed the extra IPHONEOS_DEPLOYMENT_TARGET

Colors should match the Loop standard colors; glucose should not be orange, for example. The glucose graph colors should match the normal Loop graph colors if possible. The weight of the glucose points should be adjusted for the more dense display (right now all the green dots run into each other), and the forecast should be thin long dashed lines.

We generally try to avoid jargon like "IOB" and "COB" in the app. I know it might take some redesign to fit it, but we've tried to maintain this, even on the tiny watch interface.

IOB -> Active Insulin
COB -> Active Carbohydrates, or Active Carbs

Thanks!

Thank you, Bastiaan and Marion, for developing and adding the Live Activity feature to the Loop. It’s a great addition to the app.
Personally, everything is good for what I need from this feature, but I thought adding the pump status (reservoir fill status) could be useful, as graphic or in digits format next to the glucose graph on the top section, and/or to the list of “Bottom Row Configuration” options. I think for people like me who use only three items in the bottom row to get a full reading of the Current Glucose number (and to keep the bottom row tidy to quickly see what is important, and with just a glance), the preferred location would be in top section next to the glucose graph, if possible. Thanks,

In reference to my comment above, these pictures are for comparing the options of having three or four items in the bottom row. Personally, I find three items to be optimal in this current view design.

Reporting a display glitch when using 24 hour clock. Note the time stamp (for 13:00), shows a 1.

Hi @ps2 - A question as I'm working on this:

Colors should match the Loop standard colors; glucose should not be orange, for example. The glucose graph colors should match the normal Loop graph colors if possible.

Do you object to different glucose colors being an option, but not the default? I've updated the code to use the standard Loop blue for the glucose points and prediction line (which also now match the main graph style better), but Bastiaan's code exposes a user option for color-coding the glucose points based on whether they are high, low, or in-range.

A possible middle ground would be to retain that color coding only for the display of the current BG number below the graph, but not the graph points themselves. That could be handy for glanceability, including in the CarPlay display when driving, and on the Watch Smart Stack. There's no graph in those views, but seeing the color of the BG number out of the corner of your eye while driving would tell you whether or not you're in range, even if you don't read the number itself.

I'm working on the other issues you flagged, and hope to share something soon. @bastiaanv, is it simplest for me to PR possible changes against your branch? Then if you merge, changes would automatically feed into this PR? Or let me know if another route is preferable.

@elnjensen A PR against my branch would be the simplest flow yes. I will resolve any merge conflicts that are currently present on this PR afterwards

Update by @elnjensen!

Lock-screen	WatchOS & Carplay

Changes:

• Synced Loop dev to this PR
• Processed feedback from @ps2 (link)
• Added custom view for WatchOS & Carplay